Gartner has published its latest cycle of MES-related research — the Magic Quadrant and its companion Critical Capabilities report — and the headline isn’t really about who moved from Challenger to Leader. It’s that the analyst firm has rewritten a meaningful chunk of its evaluation criteria around AI-native functionality and composable architecture. That’s a bigger deal than a quadrant reshuffle, because it changes what “good MES” is being measured against, right as a lot of plants are heading into H2 budget cycles and multi-year renewal decisions.
If you’re a plant IT lead or manufacturing engineer who’s about to get handed a PDF of dots-in-boxes by a director asking “so which one do we buy,” this is the piece to read before that conversation happens.
What actually changed this cycle
Gartner’s MES coverage has evolved in step with the broader shift in enterprise software analysis: less emphasis on monolithic feature checklists, more emphasis on how a platform’s capabilities are packaged and how easily they can be recombined. Two things stand out in this refresh.
First, composability moved from a nice-to-have differentiator to a scored criterion in its own right. That reflects what’s actually happening in the market — Siemens, Rockwell Automation, SAP, and AVEVA have all spent the last couple of years repackaging parts of their MES and manufacturing operations management stacks into more modular, API-first components, often under unified data or platform layers (Siemens Xcelerator, Rockwell’s FactoryTalk platform investments, SAP’s Digital Manufacturing Cloud tied more tightly into its broader business technology platform, AVEVA’s data-and-AI-centric platform strategy). Gartner’s methodology is catching up to that reality rather than driving it.
Second, AI-native functionality — meaning generative and predictive capabilities built into the core product rather than bolted on as a separate analytics module — is now a explicit differentiator in both the Magic Quadrant positioning and the Critical Capabilities scoring. That covers things like natural-language query against production data, AI-assisted root-cause analysis, copilot-style interfaces for shift supervisors, and predictive quality or predictive maintenance features embedded in the MES rather than sourced from a third-party analytics layer.
The consolidation subtext
There’s also a quieter thread running through this cycle: platform consolidation. Vendors that historically sold MES as a relatively standalone product are increasingly positioning it as one module in a broader manufacturing data platform — one that also handles historian functions, quality management, and increasingly, sustainability and energy data. That’s consistent with what plant teams have been living through for a few years now: fewer standalone MES RFPs, more “manufacturing platform” RFPs where MES is a line item alongside MOM, QMS, and analytics.
None of this is scandalous or surprising if you’ve been paying attention to vendor roadmaps. What matters is that Gartner formalizing it in scored criteria changes how quadrant position gets interpreted by people several levels removed from the shop floor — namely, the finance and procurement stakeholders who will see the quadrant graphic before they see anything about your actual production environment.
Why quadrant position is the wrong thing to copy into an RFP
Here’s the practical problem. A Leader-quadrant placement is an aggregate score across Gartner’s own weighting of criteria — ability to execute and completeness of vision, further broken into things like market responsiveness, sales execution, product roadmap, and viability. None of that weighting was built around your plant. A vendor can land in the Leaders quadrant on the strength of enterprise scalability and global support footprint while being a mediocre fit for a single-site discrete manufacturer running mixed-mode production with a lot of manual work instructions. The Critical Capabilities report is more useful here because it lets you re-weight scores against specific use cases (discrete vs. process, regulated vs. unregulated, high-mix vs. high-volume) — but even that requires you to substitute Gartner’s use-case weighting for your own.
Copy-pasting quadrant rank into a procurement scorecard is a way of outsourcing a decision you’re better positioned to make than any analyst firm. Gartner doesn’t know that your genealogy requirements are driven by a specific regulatory audit history, or that your changeover frequency makes recipe management the single most important module, or that your OT network segmentation under IEC 62443 rules out certain deployment models outright.
A better way to use the report
Treat the Magic Quadrant as a long-list generator and a signal of vendor direction, not a scorecard. Then do the re-weighting work yourself:
- Pull the Critical Capabilities use-case tables, not just the quadrant graphic. The underlying capability scores by use case are more actionable than the four-box summary.
- Re-score against your actual site profile. Build your own weighted matrix — genealogy and traceability depth, ISA-95/ISA-88 model alignment, integration approach with your existing historian and ERP, OT security posture, offline/edge resilience — and assign your own weights before you look at any vendor’s marketing.
- Interrogate the “AI-native” claims specifically. Ask vendors to demonstrate, live, against your data, not a canned demo environment. A lot of AI-native positioning right now is aspirational roadmap dressed as shipped feature. Ask what’s GA today, what’s in limited availability, and what requires a separate licensing tier.
- Test composability claims against a real integration scenario. Composable architecture should mean you can swap or extend a component — a quality module, a scheduling engine — without a full platform migration. Ask for a reference architecture diagram and ask what happens when you want to replace just one piece.
- Weight vendor viability against your renewal horizon, not Gartner’s. A vendor’s market execution score reflects global enterprise momentum. Your concern is whether your specific deployment gets adequate support attention over your contract term, especially if you’re a smaller account relative to that vendor’s largest customers.
What to actually do before your next budget cycle
If MES renewal or replacement is on your H2 roadmap, use this research cycle as a prompt to update your own requirements document before you touch a vendor comparison. Get specific about where AI features would generate real value on your floor versus where they’re solving a problem you don’t have. Get specific about what composability would actually let you do — replace a scheduling module, add a supplier quality workflow, integrate a new sensor platform — versus where a more integrated, single-vendor stack genuinely serves you better because your team doesn’t have the integration bandwidth to manage a composed system.
The vendors named in this cycle’s Leaders and Visionaries quadrants are all credible options for different reasons and different plant profiles — that’s true whether the graphic says so or not. The quadrant is a starting point for a long list. The requirements document with your plant’s name on it is what actually gets you to a defensible decision.
This article was written with the assistance of artificial intelligence. While we aim for accuracy, the information may be incomplete, out of date, or incorrect, and should be independently verified before you rely on it for any decision. It is provided for general information only and does not constitute professional advice.
